DSTU2
This page is part of the FHIR Specification (v1.0.2: DSTU 2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions 
USLabReport Sender
{
"resourceType": "Conformance",
"id": "conformance-uslabreport-sender",
"text": {
"status": "generated",
"div": "<div>\n\t\t\t\n <h2>USLabReport Sender</h2>\n\t\t\t\n <p>(Requirements Definition)</p>\n\t\t\t\n <p>Published: 2014-12-02 (draft)</p>\n\t\t\t\n <p>Published by: \n <b>\n\t\t\t\t\t\n <a href=\"http://www.hl7.org/\">Published by: HL7 Orders and Observation Workgroup</a>\n\t\t\t\t\n </b> Primary Author: Eric Haas Health eData Inc\n </p>\n\t\t\t\n <p>This profile defines the expected capabilities of the USLabReport Sender actor when conforming to the \n <a href=\"uslabreport.html\">The US Laboratory Report Implementation (USLabReport)</a>. This actor is the source of a laboratory test order report and declares conformance to RESTful FHIR and FHIR profiles defined in this guide. The order reference one or more FHIR resources conforming to profiles outlined in the USLabReport guide.\n </p>\n\t\t\t\n <h2>General</h2>\n\t\t\t\n <table>\n\t\t\t\t\n <tbody>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>FHIR Version:</th>\n\t\t\t\t\t\t\n <td>0.8</td>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>Supported formats:</th>\n\t\t\t\t\t\t\n <td>xml, json</td>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\n </tbody>\n\t\t\t\n </table>\n\t\t\t\n <h2>REST behavior</h2>\n\t\t\t\n <p>\n\t\t\t\t\n <b>Mode:</b> Server\n\t\t\t\n </p>\n\t\t\t\n <p>This conformance resource assumes the USLabReport Sender is the server, in other words, operating in 'Pull' or 'Push/Pull' RESTful interface. The USLabReport Sender MUST support querying one or more resources outlined by the \n <a href=\"uslabreport-guide.html\">USLabReport Guide</a>. The USLabReport Sender MUST use all the vocabularies and value set constraints defined by the individual resource profiles used by USLabReport. The USLabReport Sender MUST implement REST behavior according to the \n <a href=\"../http.html\">FHIR specification</a> and MUST be able to handle errors gracefully from Query Responders who may not support the submitted query.\n </p>\n\t\t\t\n <p>\n\t\t\t\t\n <b>Security:</b>\n\t\t\t\n </p>\n\t\t\t\n <p>Implementations must meet the security requirements documented in the \n <a href=\"uslabreport-guide.html#assumptions\">USLabReport Guide assumptions</a>.\n </p>\n\t\t\t\n <h3>Summary</h3>\n\t\t\t\n <table class=\"grid\">\n\t\t\t\t\n <thead>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>Resource</th>\n\t\t\t\t\t\t\n <th>Search</th>\n\t\t\t\t\t\t\n <th>Read</th>\n\t\t\t\t\t\t\n <th>Read Version</th>\n\t\t\t\t\t\t\n <th>Instance History</th>\n\t\t\t\t\t\t\n <th>Resource History</th>\n\t\t\t\t\t\t\n <th>Validate</th>\n\t\t\t\t\t\t\n <th>Create</th>\n\t\t\t\t\t\t\n <th>Update</th>\n\t\t\t\t\t\t\n <th>Delete</th>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\n </thead>\n\t\t\t\t\n <tbody>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>DiagnosticReport</th>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <a title=\"Allows a user to search for existing DiagnosticReport\" href=\"#DiagnosticReport-search-type\">Yes</a>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <a title=\"Allows retrieval of a specific known DiagnosticReport\" href=\"#DiagnosticReport-read\">Yes</a>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <a title=\"Allows retrieval of a specific version of a DiagnosticReport\" href=\"#DiagnosticReport-vread\">Yes</a>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <a title=\"Allows review of changes to a DiagnosticReport over time\" href=\"#DiagnosticReport-history-instance\">Yes</a>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\t\n <td/>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <a title=\"Allows a client to verify whether a particular new DiagnosticReport or revision of an existing DiagnosticReport would be accepted based on validation and other business rules. Useful for some workflows\" href=\"#DiagnosticReport-validate\">Yes</a>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <a title=\"Allows defining a new DiagnosticReport\" href=\"#DiagnosticReport-create\">Yes</a>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <a title=\"Allows editing of an existing DiagnosticReport. Servers may choose to prohibit certain types of edits, instead requiring the creation of a new DiagnosticReport (and potentially the retiring of the existing DiagnosticReport). Servers may also limit who can change particular DiagnosticReport.\" href=\"#DiagnosticReport-update\">Yes</a>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\t\n <td/>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\n </tbody>\n\t\t\t\n </table>\n\t\t\t\n <br/>\n\t\t\t\n <br/>\n\t\t\t\n <h3>\n\t\t\t\t\n <a href=\"../diagnosticreport.html\">DiagnosticReport</a>\n\t\t\t\n </h3>\n\t\t\t\n <h4>Interactions</h4>\n\t\t\t\n <table class=\"list\">\n\t\t\t\t\n <thead>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>Name</th>\n\t\t\t\t\t\t\n <th>Description</th>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\n </thead>\n\t\t\t\t\n <tbody>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>\n\t\t\t\t\t\t\t\n <a name=\"DiagnosticReport-search-type\"> </a>\n\t\t\t\t\t\t\t\n <span>search-type</span>\n\t\t\t\t\t\t\n </th>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <p>Allows a user to search for existing DiagnosticReport</p>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>\n\t\t\t\t\t\t\t\n <a name=\"DiagnosticReport-read\"> </a>\n\t\t\t\t\t\t\t\n <span>read</span>\n\t\t\t\t\t\t\n </th>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <p>Allows retrieval of a specific known DiagnosticReport</p>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>\n\t\t\t\t\t\t\t\n <a name=\"DiagnosticReport-vread\"> </a>\n\t\t\t\t\t\t\t\n <span>vread</span>\n\t\t\t\t\t\t\n </th>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <p>Allows retrieval of a specific version of a DiagnosticReport</p>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>\n\t\t\t\t\t\t\t\n <a name=\"DiagnosticReport-history-instance\"> </a>\n\t\t\t\t\t\t\t\n <span>history-instance</span>\n\t\t\t\t\t\t\n </th>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <p>Allows review of changes to a DiagnosticReport over time</p>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>\n\t\t\t\t\t\t\t\n <a name=\"DiagnosticReport-create\"> </a>\n\t\t\t\t\t\t\t\n <span>create</span>\n\t\t\t\t\t\t\n </th>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <p>Allows defining a new DiagnosticReport</p>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>\n\t\t\t\t\t\t\t\n <a name=\"DiagnosticReport-update\"> </a>\n\t\t\t\t\t\t\t\n <span>update</span>\n\t\t\t\t\t\t\n </th>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <p>Allows editing of an existing DiagnosticReport. Servers may choose to prohibit certain types of edits, instead requiring the creation of a new DiagnosticReport (and potentially the retiring of the existing DiagnosticReport). Servers may also limit who can change particular DiagnosticReport.</p>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>\n\t\t\t\t\t\t\t\n <a name=\"DiagnosticReport-validate\"> </a>\n\t\t\t\t\t\t\t\n <span>validate</span>\n\t\t\t\t\t\t\n </th>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <p>Allows a client to verify whether a particular new DiagnosticReport or revision of an existing DiagnosticReport would be accepted based on validation and other business rules. Useful for some workflows</p>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\n </tbody>\n\t\t\t\n </table>\n\t\t\t\n <h4>Search</h4>\n\t\t\t\n <p>Supported Includes: DiagnosticReport.subject, DiagnosticReport.performer, DiagnosticReport.request, DiagnosticReport.specimen, DiagnosticReport.report</p>\n\t\t\t\n <h2>REST behavior</h2>\n\t\t\t\n <p>\n\t\t\t\t\n <b>Mode:</b> Client\n\t\t\t\n </p>\n\t\t\t\n <p>The following conformance rules assumes the USLabReport Sender is the client, in other words, operating in 'Push' RESTful interface. The USLabReport Sender MUST support querying one or more resources outlined by the \n <a href=\"uslabreport.html\">USLabReport Guide</a>. The USLabReport Sender MUST use all the vocabularies and value set constraints defined by the individual resource profiles used by USLabReport. The USLabReport Sender MUST implement REST behavior according to the \n <a href=\"../http.html\">FHIR specification</a> and MUST be able to handle errors gracefully from Query Responders who may not support the submitted query.\n </p>\n\t\t\t\n <p>\n\t\t\t\t\n <b>Security:</b>\n\t\t\t\n </p>\n\t\t\t\n <p>Implementations must meet the security requirements documented in the \n <a href=\"uslabreport.html\">USLabReport Guide assumptions</a>.\n </p>\n\t\t\t\n <h3>Summary</h3>\n\t\t\t\n <table class=\"grid\">\n\t\t\t\t\n <thead>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>Resource</th>\n\t\t\t\t\t\t\n <th>Search</th>\n\t\t\t\t\t\t\n <th>Read</th>\n\t\t\t\t\t\t\n <th>Read Version</th>\n\t\t\t\t\t\t\n <th>Instance History</th>\n\t\t\t\t\t\t\n <th>Resource History</th>\n\t\t\t\t\t\t\n <th>Validate</th>\n\t\t\t\t\t\t\n <th>Create</th>\n\t\t\t\t\t\t\n <th>Update</th>\n\t\t\t\t\t\t\n <th>Delete</th>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\n </thead>\n\t\t\t\t\n <tbody>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>DiagnosticReport</th>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <a title=\"Allows a user to search for existing DiagnosticReport\" href=\"#DiagnosticReport-search-type\">Yes</a>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <a title=\"Allows retrieval of a specific known DiagnosticReport\" href=\"#DiagnosticReport-read\">Yes</a>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <a title=\"Allows retrieval of a specific version of a DiagnosticReport\" href=\"#DiagnosticReport-vread\">Yes</a>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <a title=\"Allows review of changes to a DiagnosticReport over time\" href=\"#DiagnosticReport-history-instance\">Yes</a>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\t\n <td/>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <a title=\"Allows a client to verify whether a particular new DiagnosticReport or revision of an existing DiagnosticReport would be accepted based on validation and other business rules. Useful for some workflows\" href=\"#DiagnosticReport-validate\">Yes</a>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <a title=\"Allows defining a new DiagnosticReport\" href=\"#DiagnosticReport-create\">Yes</a>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <a title=\"Allows editing of an existing DiagnosticReport. Servers may choose to prohibit certain types of edits, instead requiring the creation of a new DiagnosticReport (and potentially the retiring of the existing DiagnosticReport). Servers may also limit who can change particular DiagnosticReport.\" href=\"#DiagnosticReport-update\">Yes</a>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\t\n <td/>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\n </tbody>\n\t\t\t\n </table>\n\t\t\t\n <br/>\n\t\t\t\n <br/>\n\t\t\t\n <h3>\n\t\t\t\t\n <a href=\"../diagnosticreport.html\">DiagnosticReport</a>\n\t\t\t\n </h3>\n\t\t\t\n <h4>Interactions</h4>\n\t\t\t\n <table class=\"list\">\n\t\t\t\t\n <thead>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>Name</th>\n\t\t\t\t\t\t\n <th>Description</th>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\n </thead>\n\t\t\t\t\n <tbody>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>\n\t\t\t\t\t\t\t\n <a name=\"DiagnosticReport-search-type\"> </a>\n\t\t\t\t\t\t\t\n <span>search-type</span>\n\t\t\t\t\t\t\n </th>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <p>Allows a user to search for existing DiagnosticReport</p>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>\n\t\t\t\t\t\t\t\n <a name=\"DiagnosticReport-read\"> </a>\n\t\t\t\t\t\t\t\n <span>read</span>\n\t\t\t\t\t\t\n </th>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <p>Allows retrieval of a specific known DiagnosticReport</p>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>\n\t\t\t\t\t\t\t\n <a name=\"DiagnosticReport-vread\"> </a>\n\t\t\t\t\t\t\t\n <span>vread</span>\n\t\t\t\t\t\t\n </th>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <p>Allows retrieval of a specific version of a DiagnosticReport</p>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>\n\t\t\t\t\t\t\t\n <a name=\"DiagnosticReport-history-instance\"> </a>\n\t\t\t\t\t\t\t\n <span>history-instance</span>\n\t\t\t\t\t\t\n </th>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <p>Allows review of changes to a DiagnosticReport over time</p>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>\n\t\t\t\t\t\t\t\n <a name=\"DiagnosticReport-create\"> </a>\n\t\t\t\t\t\t\t\n <span>create</span>\n\t\t\t\t\t\t\n </th>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <p>Allows defining a new DiagnosticReport</p>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>\n\t\t\t\t\t\t\t\n <a name=\"DiagnosticReport-update\"> </a>\n\t\t\t\t\t\t\t\n <span>update</span>\n\t\t\t\t\t\t\n </th>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <p>Allows editing of an existing DiagnosticReport. Servers may choose to prohibit certain types of edits, instead requiring the creation of a new DiagnosticReport (and potentially the retiring of the existing DiagnosticReport). Servers may also limit who can change particular DiagnosticReport.</p>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>\n\t\t\t\t\t\t\t\n <a name=\"DiagnosticReport-validate\"> </a>\n\t\t\t\t\t\t\t\n <span>validate</span>\n\t\t\t\t\t\t\n </th>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <p>Allows a client to verify whether a particular new DiagnosticReport or revision of an existing DiagnosticReport would be accepted based on validation and other business rules. Useful for some workflows</p>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\n </tbody>\n\t\t\t\n </table>\n\t\t\t\n <h4>Search</h4>\n\t\t\t\n <p>Supported Includes: DiagnosticReport.subject, DiagnosticReport.performer, DiagnosticReport.request, DiagnosticReport.specimen, DiagnosticReport.report</p>\n\t\t\n </div>"
},
"name": "USLabReport Sender",
"_name": {
"fhir_comments": [
" EH: this is the SDC template for conformance examples which I will run to generate the text "
]
},
"status": "draft",
"publisher": "Published by: HL7 Orders and Observation Workgroup. Primary Author: Eric Haas Health eData Inc",
"contact": [
{
"telecom": [
{
"system": "other",
"value": "http://www.hl7.org/"
}
]
}
],
"date": "2014-12-02",
"description": "This profile defines the expected capabilities of the USLabReport Sender actor when conforming to the [[uslabreport.html|The US Sender Report Implementation (USLabReport)]]. This actor is the source of a laboratory test order report and declares conformance to RESTful FHIR and FHIR profiles defined in this guide. The order reference one or more FHIR resources conforming to profiles outlined in the USLabReport guide.",
"kind": "requirements",
"fhirVersion": "1.0.0",
"acceptUnknown": "extensions",
"format": [
"xml",
"json"
],
"rest": [
{
"fhir_comments": [
" EH: need to distinguish when laboratory in server mode = Pull: The source is a server, and the destination is a client. When the client wants to use the data, it uses a combination of search and read so the users can find the data they need\nPush/Pull: The source is a server, and the destination is a client. On a regular basis, the destination queries the server for its history, and replicates the changes in its own copy of the database\n...\nor when laboratory in client mode =Push: The source is a client, and when new data is available, it uses create, update, and transaction to push data to the destination, which is a server "
],
"mode": "server",
"documentation": "This conformance resource assumes the USLabReport Sender is the server, in other words, operating in 'Pull' or 'Push/Pull' RESTful interface. The USLabReport Sender MUST support querying one or more resources outlined by the [[uslabreport|USLabReport Guide]]. The USLabReport Sender MUST use all the vocabularies and value set constraints defined by the individual resource profiles used by USLabReport. The USLabReport Sender MUST implement REST behavior according to the [[http|FHIR specification]] and MUST be able to handle errors gracefully from Query Responders who may not support the submitted query.",
"security": {
"description": "Implementations must meet the security requirements documented in the [[uslabreport|USLabReport Guide assumptions]]."
},
"resource": [
{
"type": "DiagnosticReport",
"profile": {
"reference": "dr-uslab"
},
"interaction": [
{
"code": "search-type",
"_code": {
"fhir_comments": [
" EH: comment out for now extension url=\"http://hl7.org/fhir/StructureDefinition/conformance-expectation\">\n <valueCode value=\"SHALL\"/>\n </extension "
]
},
"documentation": "Allows a user to search for existing DiagnosticReport"
},
{
"code": "read",
"_code": {
"fhir_comments": [
" EH: comment out for now extension url=\"http://hl7.org/fhir/StructureDefinition/conformance-expectation\">\n <valueCode value=\"SHALL\"/>\n </extension "
]
},
"documentation": "Allows retrieval of a specific known DiagnosticReport"
},
{
"code": "vread",
"_code": {
"fhir_comments": [
" EH: comment out for now extension url=\"http://hl7.org/fhir/StructureDefinition/conformance-expectation\">\n <valueCode value=\"SHALL\"/>\n </extension "
]
},
"documentation": "Allows retrieval of a specific version of a DiagnosticReport"
},
{
"code": "history-instance",
"_code": {
"fhir_comments": [
" EH: comment out for now extension url=\"http://hl7.org/fhir/StructureDefinition/conformance-expectation\">\n <valueCode value=\"SHALL\"/>\n </extension "
]
},
"documentation": "Allows review of changes to a DiagnosticReport over time"
},
{
"code": "create",
"_code": {
"fhir_comments": [
" EH: comment out for now extension url=\"http://hl7.org/fhir/StructureDefinition/conformance-expectation\">\n <valueCode value=\"SHALL\"/>\n </extension "
]
},
"documentation": "Allows defining a new DiagnosticReport"
},
{
"code": "update",
"_code": {
"fhir_comments": [
" EH: comment out for now extension url=\"http://hl7.org/fhir/StructureDefinition/conformance-expectation\">\n <valueCode value=\"SHALL\"/>\n </extension "
]
},
"documentation": "Allows editing of an existing DiagnosticReport. Servers may choose to prohibit certain types of edits, instead requiring the creation of a new DiagnosticReport (and potentially the retiring of the existing DiagnosticReport). Servers may also limit who can change particular DiagnosticReport."
},
{
"code": "validate",
"_code": {
"fhir_comments": [
" EH: comment out for now extension url=\"http://hl7.org/fhir/StructureDefinition/conformance-expectation\">\n <valueCode value=\"SHOULD\"/>\n </extension "
]
},
"documentation": "Allows a client to verify whether a particular new DiagnosticReport or revision of an existing DiagnosticReport would be accepted based on validation and other business rules. Useful for some workflows"
}
],
"searchInclude": [
"DiagnosticReport.subject, DiagnosticReport.performer, DiagnosticReport.request, DiagnosticReport.specimen, DiagnosticReport.report"
]
}
]
},
{
"fhir_comments": [
" EH: comment out for now\n\t\t<searchParam ",
" EH: comment out for now extension url=\"http://hl7.org/fhir/StructureDefinition/conformance-expectation\">\n <valueCode value=\"SHALL\"/>\n </extension ",
" name value=\"category\"/>\n <definition value=\"http://hl7.org/fhir/StructureDefinition/dataelement#category\"/>\n <type value=\"token\"/>\n </searchParam>\n <searchParam ",
" interaction. operation "
],
"mode": "client",
"documentation": "The following conformance rules assumes the USLabReport Sender is the client, in other words, operating in 'Push' RESTful interface. The USLabReport Sender MUST support querying one or more resources outlined by the [[uslabreport|USLabReport Guide]]. The USLabReport Sender MUST use all the vocabularies and value set constraints defined by the individual resource profiles used by USLabReport. The USLabReport Sender MUST implement REST behavior according to the [[http|FHIR specification]] and MUST be able to handle errors gracefully from Query Responders who may not support the submitted query.",
"security": {
"description": "Implementations must meet the security requirements documented in the [[uslabreport|USLabReport Guide assumptions]]."
},
"resource": [
{
"type": "DiagnosticReport",
"profile": {
"reference": "do-uslab"
},
"interaction": [
{
"code": "search-type",
"_code": {
"fhir_comments": [
" EH: comment out for now extension url=\"http://hl7.org/fhir/StructureDefinition/conformance-expectation\">\n <valueCode value=\"SHALL\"/>\n </extension "
]
},
"documentation": "Allows a user to search for existing DiagnosticReport"
},
{
"code": "read",
"_code": {
"fhir_comments": [
" EH: comment out for now extension url=\"http://hl7.org/fhir/StructureDefinition/conformance-expectation\">\n <valueCode value=\"SHALL\"/>\n </extension "
]
},
"documentation": "Allows retrieval of a specific known DiagnosticReport"
},
{
"code": "vread",
"_code": {
"fhir_comments": [
" EH: comment out for now extension url=\"http://hl7.org/fhir/StructureDefinition/conformance-expectation\">\n <valueCode value=\"SHALL\"/>\n </extension "
]
},
"documentation": "Allows retrieval of a specific version of a DiagnosticReport"
},
{
"code": "history-instance",
"_code": {
"fhir_comments": [
" EH: comment out for now extension url=\"http://hl7.org/fhir/StructureDefinition/conformance-expectation\">\n <valueCode value=\"SHALL\"/>\n </extension "
]
},
"documentation": "Allows review of changes to a DiagnosticReport over time"
},
{
"code": "create",
"_code": {
"fhir_comments": [
" EH: comment out for now extension url=\"http://hl7.org/fhir/StructureDefinition/conformance-expectation\">\n <valueCode value=\"SHALL\"/>\n </extension "
]
},
"documentation": "Allows defining a new DiagnosticReport"
},
{
"code": "update",
"_code": {
"fhir_comments": [
" EH: comment out for now extension url=\"http://hl7.org/fhir/StructureDefinition/conformance-expectation\">\n <valueCode value=\"SHALL\"/>\n </extension "
]
},
"documentation": "Allows editing of an existing DiagnosticReport. Servers may choose to prohibit certain types of edits, instead requiring the creation of a new DiagnosticReport (and potentially the retiring of the existing DiagnosticReport). Servers may also limit who can change particular DiagnosticReport."
},
{
"code": "validate",
"_code": {
"fhir_comments": [
" EH: comment out for now extension url=\"http://hl7.org/fhir/StructureDefinition/conformance-expectation\">\n <valueCode value=\"SHOULD\"/>\n </extension "
]
},
"documentation": "Allows a client to verify whether a particular new DiagnosticReport or revision of an existing DiagnosticReport would be accepted based on validation and other business rules. Useful for some workflows"
}
],
"searchInclude": [
"DiagnosticReport.subject, DiagnosticReport.performer, DiagnosticReport.request, DiagnosticReport.specimen, DiagnosticReport.report"
]
}
]
}
]
}
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.
© HL7.org 2011+. FHIR DSTU2 (v1.0.2-7202) generated on Sat, Oct 24, 2015 07:44+1100.
Links: Search |
Version History |
Table of Contents |
Compare to DSTU1 |
|
Propose a change